Resource ValueSet/FHIR Server from package us.nlm.vsac#0.21.0 (125 ms)
Package | us.nlm.vsac |
Type | ValueSet |
Id | Id |
FHIR Version | R4 |
Source | http://fhir.org/packages/us.nlm.vsac/https://vsac.nlm.nih.gov/valueset/2.16.840.1.113883.11.20.9.19/expansion |
Url | http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.19 |
Version | 20240606 |
Status | active |
Date | 2024-06-06T01:23:01-04:00 |
Name | ProblemActStatusCode |
Title | ProblemAct statusCode |
Experimental | False |
Realm | us |
Authority | hl7 |
Description | This template reflects an ongoing concern on behalf of the provider that placed the allergy on a patient?s allergy list. As long as the underlying condition is of concern to the provider (i.e., as long as the allergy, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode is ?active?. Only when the underlying allergy is no longer of concern is the statusCode set to ?completed?. The effectiveTime reflects the time that the underlying allergy was felt to be a concern.
The statusCode of the Allergy Concern Act is the definitive indication of the status of the concern, whereas the effectiveTime of the nested Allergy - Intolerance Observation is the definitive indication of whether or not the underlying allergy is resolved. |
Purpose | (Clinical Focus: This describes the state of care giver or system interest in the associated health concern.),(Data Element Scope: StatusCode which tracks the interest in continued tracking of AllergyConcernAct or ProblemConcernAct),(Inclusion Criteria: ),(Exclusion Criteria: ) |
Resources that use this resource
Resources that this resource uses
Source
{
"resourceType" : "ValueSet",
"id" : "2.16.840.1.113883.11.20.9.19",
"meta" : {
"versionId" : "20",
"lastUpdated" : "2024-06-06T01:23:01.000-04:00",
"profile" : [
"http://hl7.org/fhir/StructureDefinition/shareablevalueset",
"http://hl7.org/fhir/us/cqfmeasures/StructureDefinition/computable-valueset-cqfm",
"http://hl7.org/fhir/us/cqfmeasures/StructureDefinition/publishable-valueset-cqfm"
]
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/valueset-author",
"valueContactDetail" : {
"name" : "HL7 US Realm Program Management Author"
}
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/resource-lastReviewDate",
"valueDate" : "2024-06-06"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/valueset-effectiveDate",
"valueDate" : "2024-06-06"
}
],
"url" : "http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.19",
"identifier" : [
{
"system" : "urn:ietf:rfc:3986",
"value" : "urn:oid:2.16.840.1.113883.11.20.9.19"
}
],
"version" : "20240606",
"name" : "ProblemActStatusCode",
"title" : "ProblemAct statusCode",
"status" : "active",
"date" : "2024-06-06T01:23:01-04:00",
"publisher" : "HL7 US Realm Program Management Steward",
"description" : "This template reflects an ongoing concern on behalf of the provider that placed the allergy on a patient?s allergy list. As long as the underlying condition is of concern to the provider (i.e., as long as the allergy, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode is ?active?. Only when the underlying allergy is no longer of concern is the statusCode set to ?completed?. The effectiveTime reflects the time that the underlying allergy was felt to be a concern.\nThe statusCode of the Allergy Concern Act is the definitive indication of the status of the concern, whereas the effectiveTime of the nested Allergy - Intolerance Observation is the definitive indication of whether or not the underlying allergy is resolved.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "urn:iso:std:iso:3166",
"code" : "US"
}
]
}
],
"purpose" : "(Clinical Focus: This describes the state of care giver or system interest in the associated health concern.),(Data Element Scope: StatusCode which tracks the interest in continued tracking of AllergyConcernAct or ProblemConcernAct),(Inclusion Criteria: ),(Exclusion Criteria: )",
"compose" : {
"include" : [
{
"system" : "http://terminology.hl7.org/CodeSystem/v3-ActStatus",
"concept" : [
{
"code" : "aborted",
"display" : "aborted"
},
{
"code" : "active",
"display" : "active"
},
{
"code" : "completed",
"display" : "completed"
},
{
"code" : "suspended",
"display" : "suspended"
}
]
}
]
},
"expansion" : {
"identifier" : "urn:uuid:039ca3be-20cd-4be2-a695-919f6b9d2435",
"timestamp" : "2024-12-10T09:56:33-05:00",
"total" : 4,
"contains" : [
{
"system" : "http://terminology.hl7.org/CodeSystem/v3-ActStatus",
"version" : "2023-02-01",
"code" : "aborted",
"display" : "aborted"
},
{
"system" : "http://terminology.hl7.org/CodeSystem/v3-ActStatus",
"version" : "2023-02-01",
"code" : "active",
"display" : "active"
},
{
"system" : "http://terminology.hl7.org/CodeSystem/v3-ActStatus",
"version" : "2023-02-01",
"code" : "completed",
"display" : "completed"
},
{
"system" : "http://terminology.hl7.org/CodeSystem/v3-ActStatus",
"version" : "2023-02-01",
"code" : "suspended",
"display" : "suspended"
}
]
},
"text" : {
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.